Closed Bug 1936673 Opened 6 months ago Closed 6 months ago

Telemetry should be able to differentiate between search modes from the one-off row vs those from the unified search button

Categories

(Firefox :: Address Bar, task, P1)

Product:
Firefox
Component:
Address Bar
Type:
task

Tracking

()

Status:
VERIFIED FIXED
Milestone:
135 Branch
Tracking Flags:
Tracking Status
firefox135 --- fixed
firefox136 --- verified

People

(Reporter: cbellini, Assigned: daisuke)

References

(Blocks 1 open bug)

Details

(Whiteboard: [sng-scotchbonnet])

Attachments

(1 file)

Bug 1936673: Add telemetry for Unified Search Button
48 bytes, text/x-phabricator-request
Details | Review

Previous to Scotch Bonnet, there is telemetry that is captured to understand when search engines and local searches (e.g. bookmarks, history, tabs) were initiated from the one-off row in the urlbar's results panel.

We will need new values to differentiate from engagements from the old one-off row to those from the new unified search button in Scotch Bonnet.

Blocks: 1891862
Severity: -- → S1
tracking-firefox134: --- → ?
tracking-firefox135: --- → ?
Priority: -- → P1
Whiteboard: [sng-scotchbonnet]
Assignee: nobody → daisuke
Status: NEW → ASSIGNED
Summary: Telemetry should be able to differentiate between search modes from the one-off row vs those from the unisified search button → Telemetry should be able to differentiate between search modes from the one-off row vs those from the unified search button

Please don't set bugs as S1 unless it is really an S1. This level of severity corresponds to a chemspill situation requiring an immediate unplanned dot release.
https://wiki.mozilla.org/BMO/UserGuide/BugFields#bug_severity

S1 (Catastrophic) Blocks development/testing, may impact more than 25% of users, causes data loss, likely dot release driver, and no workaround available

Thanks

Severity: S1 → --
Type: defect → task
tracking-firefox134: ? → ---
tracking-firefox135: ? → ---
Priority: P1 → --
Severity: -- → S1
tracking-firefox134: --- → ?
tracking-firefox135: --- → ?
Priority: -- → P1
Severity: S1 → --
tracking-firefox134: ? → ---
tracking-firefox135: ? → ---
Priority: P1 → --
Severity: -- → N/A
Priority: -- → P1
Pushed by dakatsuka.birchill@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/028c3fc2eb5d Add telemetry for Unified Search Button r=daleharvey

https://hg.mozilla.org/mozilla-central/rev/028c3fc2eb5d

Status: ASSIGNED → RESOLVED
Closed: 6 months ago
status-firefox135: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 135 Branch

Can you please summarise the telemetry probes that are found in the fix?
Thank you!

Flags: needinfo?(daisuke)
Regressions: 1938330
Regressions: 1938244
Flags: in-qa-testsuite?(aflorinescu)
Regressions: 1938142
Flags: qe-verify+

(In reply to Ardelean Oana, Desktop Test Engineering [:oardelean] from comment #5)

Can you please summarise the telemetry probes that are found in the fix?
Thank you!

I'm so sorry for my late reply!
Can the below explain it?
https://searchfox.org/mozilla-central/rev/6b61714b224f8cdca1a48ef1c51edab027f2c09f/browser/components/urlbar/metrics.yaml#2195-2229

Flags: needinfo?(daisuke)

The fix and corresponding telemetry pings were verified in the Nightly 136 Scotch Bonnet testrun.

Status: RESOLVED → VERIFIED
status-firefox136: --- → verified
Flags: qe-verify+
Flags: in-qa-testsuite?(aflorinescu) → in-qa-testsuite+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: